Management system, virtual communication-function management node, and management method

ABSTRACT

Leakage of detailed information for implementing a virtual server to execute a communication process on virtualization resources is prevented. There is provided a management system ( 10 ) included in a mobile communication system ( 1 ) configured to include an NFVI ( 60 ) which is virtualization resources including a physical server generated by a VNF ( 70 ) to execute a communication process, and the system includes a VNFM ( 30 ) for managing the VNF ( 70 ), a VIM ( 40 ) for managing the virtualization resources of the NFVI ( 60 ), an orchestrator ( 20 ) for managing all the virtualization resources of the NFVI ( 60 ), wherein the VNFM ( 30 ) includes a retention section ( 31 ) configured to retain detailed information for implementing the VNF ( 70 ) and a virtual server generation request section ( 32 ) configured to request the VIM ( 40 ) to generate the VNF ( 70 ) using the detailed information.

TECHNICAL FIELD

The present invention relates to a management system related tomanagement of a communication system, a virtual communication-functionmanagement node, and a management method.

BACKGROUND ART

Conventionally, a computer operates as a virtual machine (VM) accordingto server virtualization technology for various purposes. Also,according to this technology, designating a node in a core network of amobile communication network as the virtual machine is beinginvestigated (for example, see Non-Patent Literature 1).

CITATION LIST Non-Patent Literature

[Non-Patent Literature 1] ETSI Group Specification (ETSI GS NFV 002v1.1.1 (2013. 10)) Network Functions Virtualization (NFV); ArchitecturalFramework

SUMMARY OF INVENTION Technical Problem

A node in a core network of a mobile communication network isimplemented, for example, by a virtual network function (VNF) which is acommunication function virtualized in virtual machine(s). Management ofthe above-described mobile communication network by three functionalentities of a VNF manager (VNFM), a virtual infrastructure manager(VIM), and an orchestrator is considered. The VNFM has a function ofretaining detailed information for implementing the VNF in the virtualmachine(s) and managing the VNF. The VIM monitors a state of a physicalserver (physical server and virtualization resources) on which virtualmachine(s) is implemented and generates and deletes the virtualmachine(s) and the VNF on the physical server according to control fromthe VNFM or the orchestrator.

Also, a plurality of physical servers are generally collectivelyarranged in a data center and the VIM performs a process for a physicalserver group installed in one or more data centers. Also, the management(resource management) of the physical server group in the data center isperformed in a different mounting scheme such as OPENS TACK (registeredtrademark) or vCenter. The VIM is provided in each mounting scheme inthe data center. The orchestrator performs the overall resourcemanagement across a plurality of VIMs.

An internal structure of a node (communication node) constituting amobile communication network that is not currently virtualized differsaccording to a vendor who provides the node. The internal structurebecomes the design know-how of each vendor.

When this node is virtualized as the VNF, the VIM reservesvirtualization resources and then generates virtual machine(s) on thereserved virtualization resources and generates the VNF in the virtualmachine(s). Also, detailed information retained by the VNFM forimplementing the VNF in the virtual machine(s) is necessary to generatethe VNF in the virtual machine(s). The detailed information correspondsto the above-described internal structure of a node which is notvirtualized and includes the design know-how of each vendor.

The above-described three function entities may be provided by differentvendors. When the VNF is implemented, there is the following problem ina configuration in which the detailed information retained by the VNFMis output to, for example, another functional entity such as anorchestrator. That is, when the orchestrator and the VNFM are providedfrom different vendors, there is a risk in that the detailed information(internal structure) of the VNF is transferred to the orchestratorvendor and the know-how is leaked. Thus, this becomes an impediment ofmulti-vendor applications.

The present invention has been made in view of the above-describedcircumstances and an objective of the invention is to provide amanagement system, a virtual communication-function management node, anda management method capable of preventing the leakage of detailedinformation for implementing a virtual server to execute a communicationprocess on virtualization resources.

Solution to Problem

To accomplish the above-described objective, a management systemaccording to an embodiment of the present invention is a managementsystem which is included in a communication system configured to includevirtualization resources including a physical server in which a virtualserver for executing a communication process is generated and whichincludes a virtual communication-function management node for managing afunction of executing the communication process provided in the virtualserver, a virtualization resource management node for managing thevirtualization resources, and an overall management node for managingall the virtualization resources, wherein the virtualization resourcemanagement node includes: a monitoring means configured to monitor a usestate of the virtualization resources; a reservation means configured toperform reservation by receiving a request of the reservation ofnecessary resources for generation of the virtual server among thevirtualization resources; and a virtual server generation meansconfigured to generate the virtual server by receiving a request forgenerating the virtual server on the necessary resources for thegeneration of the virtual server reserved by the reservation means,wherein the overall management node includes: a request reception meansconfigured to receive a request related to a function of thecommunication process accompanied by the generation of the virtualserver in the physical server, and wherein the management systemincludes: a reservation request means configured to calculate thenecessary resources for the generation of the virtual server on thebasis of the request received by the request reception means and the usestate of the virtualization resources monitored by the monitoring meansand request the virtualization resource management node to perform thereservation, and wherein the virtual communication-function managementnode includes: a retention means configured to retain detailedinformation for implementing the virtual server on the virtualizationresources; and a virtual server generation request means configured togenerate the request for generating the virtual server on the necessaryresources reserved by the reservation means using the detailedinformation retained by the retention means for the virtualizationresource management node.

In the management system according to the embodiment of the presentinvention, the detailed information to be retained by the virtualcommunication-function management node is used and the virtualizationresource management node is requested to generate the virtual server.Accordingly, the notification of the detailed information from thevirtual communication-function management node to the overall managementnode is unnecessary to generate the virtual server. That is, accordingto the management system according to the embodiment of the presentinvention, it is possible to prevent the leakage of detailed informationfor implementing a virtual server to execute a communication process onvirtualization resources.

The management system may include a plurality of virtualization,resource management nodes configured to manage the virtualizationresources in mutually different schemes, wherein the virtual servergeneration request means requests the generation of the virtual serverby rewriting the detailed information according to a virtualizationresource management schemes by the virtualization resource managementnode. According to this configuration, the virtual server isappropriately generated even when the virtualization resources aremanaged in a different scheme for each virtualization resourcemanagement node.

A virtual communication-function management node included in theabove-described communication system has a novel configuration andcorresponds to the invention. That is, a virtual communication-functionmanagement node according to an embodiment of the present invention is avirtual communication-function management node in a management systemwhich is included in a communication system configured to includevirtualization resources including a physical server in which a virtualserver for executing a communication process is generated and whichincludes the virtual communication-function management node for managinga function of executing the communication process provided in thevirtual server, a virtualization resource management node for managingthe virtualization resources, and an overall management node formanaging all the virtualization resources, the virtualcommunication-function management node including: a retention meansconfigured to retain detailed information for implementing the virtualserver on the virtualization resources; and a virtual server generationrequest means configured to request the virtualization resourcemanagement node to generate the virtual server on the reserved resourcesnecessary for the generation of the virtual server among thevirtualization resources using the detailed information retained by theretention means.

The present invention can be described as the invention of themanagement system and the virtual communication-function management nodeand can also be described as the invention of the management method asfollows. These have only different categories and are substantially thesame invention and have similar operations and effects.

That is, a management method according to an embodiment of the presentinvention is a management method which is a method of operating amanagement system which is included in a communication system configuredto include virtualization resources including a physical server in whicha virtual server for executing a communication process is generated andwhich includes a virtual communication-function management node formanaging a function of executing the communication process provided inthe virtual server, a virtualization resource management node formanaging the virtualization resources, and an overall management nodefor managing all the virtualization resources, wherein the virtualcommunication-function management node includes: a retention meansconfigured to retain detailed information for implementing the virtualserver on the virtualization resources, and wherein the managementmethod includes: a monitoring step of monitoring, by the virtualizationresource management node, a use state of the virtualization resources; areservation step of performing, by the virtualization resourcemanagement node, reservation by receiving a request of a reservation ofa resources necessary for the generation of the virtual server among thevirtualization resources; a virtual server generation step ofgenerating, by the virtualization resource management node, the virtualserver by receiving a request for generating the virtual server on thenecessary resources for the generation of the virtual server reserved inthe reservation step; a request reception step of receiving, by theoverall management node, a request related to a function of thecommunication process accompanied by the generation of the virtualserver in the physical server; a reservation request step ofcalculating, by the management system, the necessary resources for thegeneration of the virtual server on the basis of the request received inthe request reception step and the use state of the virtualizationresources monitored in the monitoring step and requesting thevirtualization resource management node to perform the reservation; anda virtual server generation request step of requesting, by the virtualcommunication-function management node, the generation of the virtualserver on the necessary resources reserved in the reservation step usingthe detailed information retained by the retention means for thevirtualization resource management node.

Also, a management method according to an embodiment of the presentinvention is a management method which is a method of operating avirtual communication-function management node in a management systemwhich is included in a communication system configured to includevirtualization resources including a physical server in which a virtualserver for executing a communication process is generated and whichincludes the virtual communication-function management node for managinga function of executing the communication process provided in thevirtual server, a virtualization resource management node for managingthe virtualization resources, and an overall management node formanaging all the virtualization resources, wherein the virtualcommunication-function management node includes: a retention meansconfigured to retain detailed information for implementing the virtualserver on the virtualization resources, and wherein the managementmethod includes: a virtual server generation request step of requestingthe virtualization resource management node to generate the virtualserver on the reserved resources necessary for the generation of thevirtual server among the virtualization resources using the detailedinformation retained by the retention means.

Advantageous Effects of Invention

According to an embodiment of the present invention, it is possible toprevent leakage of detailed information for implementing a virtualserver to execute a communication process on virtualization resourcesbecause a virtual server is generated without having to providenotification of detailed information from a virtualcommunication-function management node to an overall management node.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram illustrating a configuration of a management systemand a mobile communication system including the management systemaccording to an embodiment of the present invention.

FIG. 2 is a diagram illustrating a functional configuration of themanagement system according to an embodiment of the present invention.

FIG. 3 is a diagram illustrating a hardware configuration of a nodeincluded in the management system according to an embodiment of thepresent invention.

FIG. 4 is a table storing information to be used in the managementsystem.

FIG. 5 is a table storing information to be used in the managementsystem,

FIG. 6 is a table storing information to be used in the managementsystem.

FIG. 7 is a table storing information to be used in the managementsystem.

FIG. 8 is a table storing information to be used in the managementsystem.

FIG. 9 is a table storing information to be used in the managementsystem.

FIG. 10 is a table storing information to be used in the managementsystem.

FIG. 11 is a table storing information to be used in the managementsystem.

FIG. 12 is a table storing information to be used in the managementsystem.

FIG. 13 is a table storing information to be used in the managementsystem.

FIG. 14 is a table storing information to be used in the managementsystem.

FIG. 15 is a sequence diagram illustrating a process management method)to be executed during instantiation in the management system accordingto an embodiment of the present invention.

FIG. 16 is a sequence diagram illustrating a process management method)to be executed during instantiation in the management system accordingto an embodiment of the present invention.

FIG. 17 is a sequence diagram illustrating a process management method)to be executed during auto-healing in the management system according toan embodiment of the present invention.

FIG. 18 is a sequence diagram illustrating a process (management method)to be executed during auto-healing in the management system according toan embodiment of the present invention.

FIG. 19 is a sequence diagram illustrating a process management method)to be executed during scale-out in the management system according to anembodiment of the present invention.

FIG. 20 is a sequence diagram illustrating a process management method)to be executed during scale-out in the management system according to anembodiment of the present invention.

FIG. 21 is a sequence diagram illustrating a process management method)to be executed during scale-in in the management system according to anembodiment of the present invention.

FIG. 22 is a sequence diagram illustrating a process management method)to be executed during scale-in in the management system according to anembodiment of the present invention.

FIG. 23 is a diagram conceptually illustrating instantiation, scale-out,and scale-in.

FIG. 24 is a flowchart illustrating a process of determining a unit ofenhancement.

FIG. 25 is a flowchart illustrating a process of determining a unit ofreduction.

FIG. 26 is a table storing necessary information for enhancement orreduction in units of internal functional sections.

FIG. 27 is a table illustrating a relationship between a performanceincrease/decrease unit of a virtualization function and an embodiment.

FIG. 28 is a diagram illustrating a variation of the embodiment of thepresent invention.

DESCRIPTION OF EMBODIMENTS

Hereinafter, embodiments of a management system, a virtualcommunication-function management node, and a management methodaccording to the present invention will be described in detail withreference to the drawings. Also, the same elements are assigned the samereference signs and redundant description thereof will be omitted.

FIG. 1 is a diagram illustrating a configuration of a mobilecommunication system 1 including the management system 10 according tothe present embodiment. The mobile communication system 1 is a systemfor providing a function of mobile communication to a mobilecommunication terminal (mobile station) (not illustrated). The mobilecommunication terminal is an apparatus that is used by a user andconnects to the mobile communication system (mobile communicationnetwork) through wireless communication to perform mobile communication.Specifically, the mobile communication terminal corresponds to aportable telephone or the like. For example, the mobile communicationterminal performs communication by establishing a call connection withan opposite node via the mobile communication system 1. The oppositenode corresponds to, for example, another mobile communication terminalor a server apparatus for providing various services to the mobilecommunication terminal, an apparatus (for example, a mobility managemententity (MIME) a serving gateway (S-GW), or a PDN gateway (P-GW)) forconnecting to another communication network, or the like. The mobilecommunication terminal can perform mobile communication, for example,when a user of the mobile communication terminal makes a contract with acommunication provider of the mobile communication system 1. Also, themobile communication terminal may be similar to a conventional mobilecommunication terminal.

As illustrated in FIG. 1, the management system 10 is configured toinclude the orchestrator 20, a VNFM 30, and a VIM 40. Also, the mobilecommunication system 1 is configured to include an operations supportsystem/business support system (OSS/BSS) 50, an NFV infrastructure(NFVI) 60, a virtual network function (VNF) 70, and an elementmanagement system (EMS) 80. These components constitute a core networkof a mobile communication system 1 (mobile communication network). Also,components between which mutual transmission/reception of information isnecessary are connected by wire or the like to enable thetransmission/reception of the information.

In the mobile communication system 1 according to the presentembodiment, a communication function is provided to the mobilecommunication terminal by virtual server(s) operating in virtualmachine(s) implemented on a physical server. That is, the mobilecommunication system 1 is a virtualized mobile communication network.The communication function is provided to the mobile communicationterminal by executing a communication process according to thecommunication function through the virtual machine(s).

The NFVI 60 includes physical resources, a virtualization layer, andvirtualization resources constituting a virtualized environment. Thephysical resources include calculation resources, storage resources, andtransfer resources. The virtualization layer virtualizes the physicalresources and provides the virtualized physical resources to the VNF 70(APL) (for example, a hypervisor). The virtualization resources arevirtualized infrastructure resources to be provided to the VNF 70. Thatis, the NFVI 60 is a virtualization resource configured to include thephysical server which is a physical server apparatus for performing acommunication process in the mobile communication system 1. The physicalserver is configured to include a CPU (a core, a processor), a memory,and a storage means such as a hard disk. Generally, a plurality ofphysical servers constituting the NFVI 60 are arranged at a position ofa data center (DC) or the like. In the data center, the arrangedphysical servers are connected through a network inside the data centerand are configured to perform mutual transmission/reception ofinformation. Also, in the mobile communication system 1, a plurality ofdata centers are provided. The data centers are connected by the networkand the physical servers provided in different data centers can performmutual transmission/reception of the information via their networks.

The VNF 70 is (a function of executing a communication process providedin) virtual server(s) which is a virtual communication processing nodeto execute the communication process. The VNF 70 is implemented in theNFVI 60. The VNF 70 is implemented, for example, using virtual machine(VM) technology, by allocating the CPU provided in the NFVI 60 for theVNF 70, implementing virtual machine(s) on the allocated CPU, andexecuting a program on the virtual machine(s). The VNF 70 is generallygenerated (implemented) according to the communication process to beexecuted. Also, the VNF 70 may be configured to include a plurality ofvirtual network function components (VNFCs) which are its components.

The mobile communication system 1 includes one or more (or a pluralityof) VNFs 70. The VNF 70 corresponds to a node such as a call sessioncontrol function (CSCF) or an application server (AS) in IMS.Alternatively, for example, the VNF 70 corresponds to a node such as aserving GPRS support node (SGSN) in a general packet radio service(GPRS) system which is one of the mobile communication systems and anode such as a mobility management entity (MME) or a serving gateway(S-GW) in a Long Term Evolution/Evolved Packet Core (LTE/EPC) system.

The EMS 80 is a node for monitoring and controlling the VNF 70. The EMS80 is also virtually implemented in the NFVI 60 as in the VNF 70. TheEMS 80 is generated in association with the VNF 70 (for example, in aone-to-one relationship with the VNF 70 as illustrated in FIG. 1). TheEMS 80 monitors and controls the associated VNF 70. The EMS 80 performsfault, configuration, accounting, performance, and security (FCAPS)management of the VNF 70. The EMS 80 may be virtually implemented asdescribed above or physically implemented to avoid the complexity ofmanagement in performing the FCAPS management.

The OSS/BSS 50 is a node which performs service management in the mobilecommunication system 1 and provides the management system 10 with aninstruction related to a communication function in the mobilecommunication system 1. For example, the OSS/BSS 50 instructs themanagement system 10 to start up a new communication function(communication service). Also, the OSS/BSS 50 receives information fromthe EMS 80 and provides the management system 10 or the EMS 80 with aninstruction on the basis of the information. Also, the OSS/BSS 50 can beoperated by a communication provider related to the mobile communicationsystem 1.

The orchestrator 20 which is a component of the management system 10 isan overall management node (functional entity) for managing the entireNFVI 60 which is a virtualization resource. The orchestrator 20 receivesan instruction from (an OSS 51 of) the OSS/BSS 50 and performs a processaccording to the instruction. The orchestrator 20 performs management ofan infrastructure and communication service across all virtualizationresources of a mobile communication network. The orchestrator 20implements a communication service constituted of a plurality of VNFs 70in a proper place via the VNFM 30 and the VIM 40. For example, lifecycle management (specifically, for example, generation, update, scalecontrol, and event collection) of a service,distribution/reservation/allocation management of resources,service/instance management, and policy management (specifically, forexample, reservation/allocation, optimum arrangement of resources basedon geography/laws, etc.) across the entire mobile communication network.

The VNFM 30 which is a component of the management system 10 is avirtual communication-function management node (functional entity) whichmanages the VNF 70. A plurality of VNFMs 30 are provided in the mobilecommunication system 1. In this case, the VNFM 30 to be managed for eachVNF 70 may be predetermined. The VNFM 30 performs life cycle managementof the VNF 70 (APL). The VNFM 30 performs overall control related tovirtualization of the VNF 70. For example, it performs instancegeneration, update, scale control, termination, and auto-healing of theVNF 70.

The VIM 40, which is a component of the management system 10, is avirtualization resource management node (functional entity) whichmanages the virtualization resources (infrastructure resources) of unitsin which the VNF 70 is implemented in the NFVI 60. Specifically, itperforms management of allocation/update/collection of resources,association of virtual resources and physics, and management of lists ofhardware resources and SW resources (hypervisor). Generally, the VIM 40performs management for each data center (station building). Themanagement of the virtualization resources can be performed in a schemeaccording to the data center. A management scheme of the data center (amounting scheme of management resources) is of a type such as OPENSTACKor vCenter. Generally, the VIM 40 is provided for each management schemeof the data center. That is, the management system 10 includes aplurality of VIMs 40 which manage the virtualization resources of unitsin which the VNF 70 is implemented in the NFVI 60 in mutually differentschemes. Also, it is unnecessary for units of virtualization resourcesmanaged in different management schemes to be units of data centers.

Also, the orchestrator 20, the VNFM 30, and the VIM 40 are implementedby executing a program on a physical server apparatus (however, they arenot limited to implementation in virtualization and may be implementedin virtualization separately from the management system). Theorchestrator 20, the VNFM 30, and the VIM 40 may be implemented byseparate physical server apparatuses or implemented by the same serverapparatus. The orchestrator 20, the VNFM 30, and the VIM 40 (or programsfor implementing them) may be provided from separate vendors.

Also, the above-described architecture is based on that disclosed inNon-Patent Literature 1. Also, the mobile communication system 1 mayinclude components other than the above-described components toimplement a mobile communication function. For example, the mobilecommunication system 1 may include an apparatus of a base station, anOpenFlow network (including a virtualized element as described above),etc.

Next, functions according to the present embodiment provided in themanagement system 10 will be described. As illustrated in FIG. 2, theorchestrator 20 includes a request reception section 21 and areservation request section 22. The request reception section 21 is arequest reception means which receives a request related to a functionof a communication process accompanied by the generation of the VNF 70in the physical server included in the NFVI 60 from (the OSS 51 of) theOSS/BSS 50.

The reservation request section 22 is a reservation request means whichrequests the VIM 40 to reserve necessary resources for the generation ofthe VNF 70 in the NFVI 60 by calculating the necessary resources for thegeneration of the VNF 70 on the basis of a request received by therequest reception section 21, a use state of the NFVI 60 monitored bythe VIM 40, information from the VNFM 30, etc.

As illustrated in FIG. 2, the VNFM 30 includes a retention section 31and a virtual server generation request section 32. The retentionsection 31 is a retention means which retains detailed information forimplementing the VNF 70 on the NFVI 60. The virtual server generationrequest section 32 is a virtual server generation request means whichrequests the VIM 40 to generate the VNF 70 on necessary resourcesreserved in the NFVI 60 using the detailed information retained in theretention section 31. Also, the VNFM 30 may request the generation ofthe VNF 70 by rewriting the detailed information according to avirtualization resource management schemes (NFVI 60) by the VIM 40.

As illustrated in FIG. 2, the VIM 40 includes a monitoring section 41, areservation section 42, and a virtual server generation section 43. Themonitoring section 41 is a monitoring means which monitors the use stateof the NFVI 60. The reservation section 42 is a reservation means whichperforms reservation by receiving a request of the reservation of thenecessary resources for the generation of the VNF 70 in the NFVI 60 fromthe orchestrator 20. The virtual server generation section 43 is avirtual server generation means which generates the VNF 70 by receivingthe request for generating the VNF 70 on the necessary resources for thegeneration of the VNF 70 reserved by the reservation section 42 from theVNFM 30.

The above function is a function related to the present embodimentprovided in the management system 10. Also, in the description of aprocess by the management system 10 using a sequence diagram, functionsof the orchestrator 20, the VNFM 30, and the VIM 40 according to thepresent embodiment will be described in more detail. Also, functionswhich are not included in the above-described functional sections areprovided in the orchestrator 20, the VNFM 30, and the VIM 40, butdescription of these functions is also included in the description ofthe process by the management system 10 using the sequence diagram.

FIG. 3 illustrates a hardware configuration of a server apparatusconstituting the orchestrator 20, the VNFM 30, and the VIM 40 includedin the management system 10 according to the present embodiment. Asillustrated in FIG. 3, the server apparatus is configured to include acomputer provided with hardware such as a CPU 101, a random accessmemory (RAM) 102 and a read only memory (ROM) 103 which are main storageapparatuses, a communication module 104 for performing communication,and an auxiliary storage apparatus 105 such as a hard disk. Thesecomponents are operated by a program, etc., so that the functions of theorchestrator 20, the VNFM 30, and the VIM 40 described above and to bedescribed below are exhibited. Also, the orchestrator 20, the VNFM 30,and the VIM 40 may be constituted of a computer system including aplurality of server apparatuses. Also, a node other than theabove-described nodes included in the mobile communication system 1 mayalso be implemented by a server apparatus having the above-describedhardware configuration. The above configuration is a configuration ofthe management system 10 according to the present embodiment.

Next, a management method which is a process to be executed by themanagement system 10 according to the present embodiment will bedescribed using tables of FIGS. 4 to 14 and sequence diagrams of FIGS.15 to 22. Hereinafter, processes when (1) instantiation, (2)auto-healing, (3) scale-out, and (4) scale-in are performed in themobile communication system 1 will be described for each of theabove-described cases. Also, FIG. 23 illustrates overviews of theinstantiation, the scale-out, and the scale-in.

First, a process when (1) instantiation is performed will be describedusing the sequence diagrams of FIGS. 15 and 16. Also, the sequencediagram illustrated in FIG. 16 is a continuation of the sequence diagramof FIG. 15 (in a time-series manner). The instantiation is thegeneration of a new VNF 70 according to the communication service toprovide a new communication service (communication function) in themobile communication system 1. According to the instantiation, the newcommunication service is provided in the mobile communication system 1.

First, in the orchestrator 20, a resource use state inquiry is performedfor each VIM 40 (S001). In the VIM 40, the monitoring section 41receives the resource use state inquiry. The monitoring section 41monitors the resource use state of the NFVI 60 serving as a managementtarget of the VIM 40. Information indicating the resource use stateobtained as a monitoring result is transmitted from the monitoringsection 41 to the orchestrator 20 as a resource use state inquiryresponse (S002, monitoring step). The orchestrator 20 receives theinformation. The processes of S001 and S002 are periodically performedfor each VIM 40.

This information is information of each data center (DC) as shown inTable T1 of FIG. 4(a) and is obtained by associating resourceinformation of the virtual machine(s) and the network (NW) andinformation indicating provided functions. That is, this information isstate information of resources of the entire mobile communication system1 (mobile communication network). The information is constantly retainedin a network total resource information database provided in theorchestrator 20.

In Table T1 of FIG. 4(a), an available bandwidth is an availablebandwidth of a communication path (of an exit of the data center)between the data center and the outside of the data center. An availableexternal address is an address assignable to the VNF 70 and is necessaryfor the VNF 70 to communicate with another VNF 70 or an element otherthan the VNF 70. The provided function is a function related tocommunication capable of being provided by dedicated hardware orsoftware in the data center. Specifically, there is a high-speed packetprocessing function (for example, DPDK of Intel Corporation), a function(for example, SR-IOV) of bypass technology of a virtualization layer, orthe like.

Next, a request (signal (1)) of service generation related to acommunication service is transmitted from (the OSS 51 of) the OSS/BSS 50to the orchestrator 20. The communication service is, for example, voicecommunication and communication in which an image or a moving image(rich media) is transmitted and received (a communication servicediffers according to each type of data to be transmitted). This requestis a request related to a function of the communication processaccompanied by the generation of the VNF 70 in the physical serverincluded in the NFVI 60. In the orchestrator 20, the request receptionsection 21 receives the signal (S003, request reception step).

The signal includes information indicating a service ID serving as anumber for uniquely identifying a generated service, a communicationservice to be generated, a performance condition, and networkinformation. Specifically, “communication service 1” in thecommunication service, “100” in the performance condition, and “DC 1connection and bandwidth of 5 Gbps or more” indicating <DC connected toDC 1 in a bandwidth of 5 Gbps or more> in the NW (network) condition areincluded (set) in the signal.

The performance condition is a normalized index value for indicatingcapability in control (generation, enhancement, reduction, or the like)for the VNF 70 and a service configured by the VNF 70. The performancecondition is pre-negotiated between the OSS 51 and the VNFM 30.

Next, the VNF 70 (virtualized function) and the VNFM 30 (managementfunction) constituting a communication service specified by informationincluded in the signal are specified from operation data pre-registeredin the orchestrator 20. Specifically, “VNF 10” and “VNF 21” serving asthe VNF 70 constituting “communication service 1” are derived from TableT2 of FIG. 5(a) which is the operation data and the fact that the VNFM30 of “VNF 10” is “VNFM 1” and the VNFM 30 of “VNF 21” is “VNFM 2” isderived from Table T3 of FIG. 5(b) which is the operation data (A,S004).

The subsequent processes of S005 to S024 are executed sequentially or inparallel in units of VNFs 70. Here, the generation of “VNF 10” is shown.

Next, the orchestrator 20 selects a data center in which “VNF 10” can bearranged using the operation condition of Table T4 of FIG. 5(c), the NWcondition input according to the signal (1), and the connectionconfiguration of the data center of Table T5 of FIG. 5(e) to generatethe above-described specified “VNF 10.” Candidates “DC 2,” “DC 3,” “DC4,” and “DC 5” can be obtained as the data center in which “VNF 10” canbe arranged from Table T4 of FIG. 5(c) pre-registered in theorchestrator 20. Next, it is determined that “DC 5” does not satisfy thecondition from “DC 1 connection and bandwidth of 5 Gbps or more” of theinput NW condition and connection information indicating that the datacenters connected to “DC 1” capable of being obtained from Table T5 ofFIG. 5(e) pre-registered in the orchestrator 20 are “DC 2,” “DC 3,” and“DC 4,” and the candidate data centers become “DC 2,” “DC 3,” and “DC4.”

Next, the orchestrator 20 reads resource information of the selected “DC2,” “DC 3,” and “DC 4” from Table T1 of FIG. 4(a) of the network totalresource information database accumulated through periodic collection.The read resource information is shown in Table T8 of FIG. 4(b). Next, aVNF identification number “VNF 001” is dispatched as a number foruniquely identifying the VNF 70 to be generated (B, S005).

Next, a combination table (Table T8 of FIG. 4(b)) of resourceinformation read to be “DC 2,” “DC 3,” and “DC 4” extracted ascandidates for the data center capable of being arranged in B (S005),“100” of the performance condition input in the signal (1), “VNF 10”serving as a generation target VNF type, and the dispatched VNFidentification number “VNF 001” are transmitted as a necessary resourceinquiry (signal (2)) to “VNFM 1” which is the VNFM 30 of “VNF 10” readin the above-described A (S004) (S006).

Also, an embodiment which does not include resource information of eachdata center in S006 is also possible. In this case, in place of theresource information of each data center, an identification number ofthe VIM 40 which manages each data center is read from Table T6 of FIG.5(d) pre-registered in the orchestrator 20 and included in informationto be transmitted in S006. For example, a combination in which the VIM40 of “DC 2” is “VIM 1,” the VIM 40 of “DC 3” is “VIM 1,” and the VIM 40of “DC 4” is “VIM 2” is included in information to be transmitted.

The signal (2) is received in “VNFM 1.” In “VNFM 1” receiving the signal(2), it is confirmed whether the resource information for each datacenter is set (whether the resource information is included in thesignal (2)). When the VIM identification number is set in place of theresource information, “VNFM 1” requests the VIM 40 to provide theresource information of each data center and collects the resourceinformation of each data center. For example, “VNFM 1” inquires of theresource information of “DC 2” and “DC 3” for “VIM 1” and the resourceinformation of “DC 4” for “VIM 2” received in the signal (2) and canobtain Table T8 of FIGS. 4(b) (S007 and S008).

In “VNFM 1” obtaining the resource information (Table T8 of FIG. 4(b))of the data center in the signal (2) or the processes of S007 and S008,detailed information of “VNF 10” set in the VNF type of the signal (2)is read from the VNF detailed information database previously retained(registered) in the retention section 31 of the “VNFM 1.” In thedetailed information, a combination of resource information (VM),resource information (NW), and function information according to a VNFinternal structure and a performance condition of Table T9 of FIG. 6 isregistered. A model number of Table T9 of FIG. 6 is an identifier ofeach combination. An image file of the resource information (VM) retainsinformation for configuring VM as a file and is used when the VNF 70starts up. The image file is pre-stored in any place within acommunication network from which the image file can be read by the VIM40. The VNF 70 is constituted of one or more internal functionalsections and resources for generating the VNF 70 are secured by the VIM40 for each internal functional section. Arrangement/startup informationincludes correspondence relationships among the resources of eachinternal functional section secured by the VIM 40 and the image file,setting information for starting up the VNF 70 using the image file, astartup procedure for each internal functional section, and a reductionprocedure for each internal functional section when the VNF 70 isdeleted. NW configuration information of the resource information (NW)is information indicating an NW connection type of the internalfunctional section of the VNF 70.

In “VNFM 1,” the resource information and the function informationnecessary for the performance condition “100” of the VNF type “VNF 10”received in the signal (2) from the read detailed information (Table T9of FIG. 6) are extracted (C1, S009).

An available data center is extracted by comparing the extractedresource information and function information with the availableresource information and the provided function of the resourceinformation (Table T8 of FIG. 4(b)) obtained in the signal (2) or theprocesses of S007 and S008. Specifically, it is determined that “VNF 10”requires “function 1” and “function 2” from Table T9 of FIG. 6 and datacenters capable of providing “function 1” and “function 2” are “DC 2”and “DC 3” from Table T8 of FIG. 4(b).

Next, necessary resource information is derived to generate the VNF 70in resources provided by an available data center. Specifically, fromTable T8 of FIG. 4(b), it can be determined that “DC 2” can provide highand low CPU performance and “DC 3” can provide low CPU performance.Here, the CPU performance indicates a classification related tocalculation performance based on an operation frequency of the CPU, thenumber of physical cores, fast calculation technology, or the like. Thisis collated with the CPU performance of Table T9 of FIG. 6 read in theprocess of S009 (it is determined that the necessary resourceinformation for the generation of the VNF 70 is available in the datacenter) and Table T10 of FIG. 7(a) can be obtained as a combination ofresource information capable of being obtained by “DC 2” and “DC 3.” Indetail, it can be seen that “VNF 10” is constituted of the internalfunctional sections “VNFC 100” and “VNFC 101” from Table T9 of FIG. 6read in the process of S009. Further, in the case of the performancecondition “100,” it can be seen that the internal functional section“VNFC 100” can be generated by virtual resources (VM and NW) of themodel number “001” using the CPU performance “High” or the model number“002” using the CPU performance “Low” and the internal functionalsection “VNFC 101” can be generated by virtual resources (VM and NW) ofthe model number “005” using the CPU performance “High” or the modelnumber “006” using the CPU performance “Low.” Therefore, the number ofcombinations of necessary virtual resources for generating the VNF 70having the performance condition “100” of the VNF type “VNF 10”indicated by the signal (2) is 4 in “DC 2” in which the CPU performance“High” and “Low” can be provided and 1 in “DC 3” in which only the CPUperformance “Low” can be provided, and Table T10 of FIG. 7(a) can beobtained. The service ID, the VNF type, and the VNF identificationnumber of the signal (2) and Table T9 of FIG. 6 of the detailedinformation are stored (C2, S010).

Next, Table T10 of FIG. 7(a) indicating the derived combination of theresource information and the data center is returned from “VNFM 1” tothe orchestrator 20 (signal (3), S011).

The orchestrator 20 receives the signal (3) through the reservationrequest section 22. Table T13 of FIG. 7(b) can be obtained by assigningpriority to the combination table (Table T10 of FIG. 7(a)) of theresource information and the data centers received in the signal (3) onthe basis of a priority index of Table T12 of FIG. 5(f) pre-registeredin the orchestrator 20. A specific procedure will be described. Firstpriority from Table T12 of FIG. 5(f) becomes a bandwidth between DCs. Itcan be seen that DCs serving as the candidates from Table T10 of FIG.7(a) are “DC 2” and “DC 3” and an NW bandwidth between “DC 1” and “DC 2”is greater than an NW bandwidth between “DC 1” and “DC 3” from Table T5of FIG. 5(e), d “DC 2” has high priority. Next, second priority fromTable T12 of FIG. 5(f) becomes the CPU performance. From Table T10 ofFIG. 7(a), it can be seen that the priority of combination 2 of only theCPU performance “High” among combinations of “DC 2” is highest and thepriority of combination 1 of only the CPU performance “Low” is lowest.For combinations 3 and 4 of the CPU performance “High” and “Low,” asmall VM storage region of third priority is used. From Table T10 ofFIG. 7(a), it can be seen that the number of VMs of 300 GB in the VMstorage region is (1+2) in combination 3, the number of VMs of 300 GB is2 and the number of VMs of 500 GB is 1 in combination 4, and thepriority of combination 3 having a small capacity of the VM storageregion is high. Thereby, Table T13 of FIG. 7(b) in which the priority isassigned to the combination of necessary resources can be obtained (D,S012).

Next, reservation of the VIM 40 for managing the data center isperformed in the order of combination of high priority. The reservationrequest section 22 sets the necessary resources of combination 2 havinghighest priority and “DC 2” of the target in Table T13 of FIG. 7(b) anda resource reservation request is transmitted to “VIM 1” which is amanagement function of “DC 2” read from Table T6 of FIG. 5(d) (signal(4), S013, reservation request step). In the case of a combination ofpriority 1 of Table T13 of FIG. 7(b), information of Table T14 of FIG.8(a) becomes necessary resource information (VM and NW) (is set asnecessary resource information). When the resource reservation fails, areservation request of the combination of the next highest priority isperformed (F, return from the process S016).

In “VIM 1,” a signal (4) is received. In “VIM 1” receiving the signal(4), the reservation section 42 confirms whether necessary resourcesshown in Table T14 of FIG. 8(a) for which “DC 2” set in the signal (4)is requested in the signal (4) can be secured on the basis of an insidemanagement area resource information database and a reservation numberfor which the resources are reserved is dispatched (E, S014, reservationstep). In “VIM 1,” the reserved “DC 2” and reserved resource information(Table T14) are stored along with the reservation number. In “VIM 1,” areservation number serving as a response when the resources can besecured and an error serving as a response when the resources cannot besecured are provided to the orchestrator 20 (signal (5), S015).

In the orchestrator 20, a signal (5) from “VIM 1” is received. In theorchestrator 20 in which the signal (5) from “VIM 1” is received, aresource reservation result is confirmed (F, S016). When the reservationof the resources is impossible (F, NG of S016), reservation of acombination of the next highest priority is performed by returning tothe process of D (S012) again.

When the reservation succeeds, the orchestrator 20 sets the service IDdispatched in the process of S005, “VIM 1” serving as a VIMidentification number of a resource reservation destination, a VIM typeobtained from Table T6 of FIG. 5(d), a reservation number received inthe signal (5) from “VIM 1,” and resource information of Table T14 ofFIG. 8(a) serving as reservation resource information (VM and NW) andrequests “VNFM 1” to generate “VNF 10” (signal (6), S017). Also, in theorchestrator 20, the service ID, the VNF type, the VNF identificationnumber, the reservation number, the reserved “VIM 1,” and the reserved“DC 2” are stored.

In “VNFM 1,” the virtual server generation request section 32 receivesthe signal (6). Next, the virtual server generation request section 32reads Table T9 of FIG. 6 of the detailed information stored in C2 (S010)from the service ID received in the signal (6) and determines thearrangement/startup information and the NW (network) configurationinformation corresponding to the model numbers “001” and “005” of TableT14 of FIG. 8(a) of the reserved resource information (VM and NW)received in the signal (6). Next, the virtual server generation requestsection 32 dispatches and assigns a VM identification number to thegenerated virtual machine (VM).

Next, in “VNFM 1,” a format of the arrangement/startup information andthe NW configuration information is changed according to the VIM typereceived in the signal (6) (detailed information is rewritten accordingto a management scheme of the VIM 40) by the virtual server generationrequest section 32 (G, S108, virtual server generation request step).Also, this rewriting can be performed according to the conventionaltechnology.

Next, the virtual server generation request section 32 notifies “VIM 1”of a reservation destination received in the signal (6) of thearrangement/startup information and the NW configuration information forwhich the format is changed for “VIM 1” and the reservation numberreceived in the signal (6) and requests “VIM 1” to generate “VNF 10”(signal (7), S109, virtual server generation request step). Informationset as the arrangement/startup information and the NW configurationinformation becomes Table T15 of FIG. 8(b). In “VNFM 1,” the service ID,the VNF type, and the VNF identifier (VNF identification number) storedin C2 (S010) are stored in association with the VIM identificationnumber and the reservation number received in the signal (6), theinternal functional section, and the VM identification number.

In “VIM 1,” the virtual server generation section 43 receives the signal(7). Next, the virtual server generation section 43 specifies resourcesof “DC 2” secured in the process of E (S014) as resources for startingup the VNF 70 from a reservation number received in the signal (7).Next, the virtual server generation section 43 reads image files of VMand VNF in “DC 2” on the basis of the arrangement/startup informationand the NW configuration information received in the signal (7) andgenerates/starts up VM and the VNF 70.

In “VIM 1,” the virtual server generation section 43 assigns “externalIP address 01” and “external IP address 02” as a number of externaladdresses designated in the signal (7) to VM from a pre-allocatedexternal IP address band. In “VIM 1,” information of Table T16 of FIG.9(a) is stored by associating the reservation number, the data center,the VM identification number of “VNFM 1,” the physical apparatus (HW),the allocated resource information, and the transmission source VNFM 30of the signal (7) (H, S020, virtual server generation step).

Next, the virtual server generation section 43 provides “VNFM 1” with aresponse of Table T17 of FIG. 9(b) in which a correspondence relation of“external IP address 01” and “external IP address 02” allocated duringVM generation and VM is set as the NW (network) information in a signal(8) (S021 of FIG. 16).

In “VNFM 1,” the NW information set in the signal (8) is added toinformation associated with a service ID stored in the process of G(S018) and stored. Content of the information becomes Table T18 of FIG.9(c) (J, S022).

When VNF generation succeeds, a notification of the signal (9) in which“external IP address 01” and “external IP address 02” are set as NWinformation is provided from “VNFM 1” to the orchestrator 20 (S023).

In the orchestrator 20, the signal (9) is received. In the orchestrator20 receiving the signal (9), it is confirmed that the VNF generation iscompleted. In the orchestrator 20, the information of the VNF 70 storedin the process of S017 and the NW information set in the signal (9) arestored in association with the service ID. Content of the informationbecomes Table T19 of FIG. 9(d) (K, S024).

For “VNF 21,” procedures of B to K (processes of S005 to S024) aresimilarly executed. In the orchestrator 20, Table T21 of FIG. 10(a) inwhich a result of generating “VNF 21” is reflected in a result of “VNF10” can be obtained. “VNF 21” is assumed to be generated in the samedata center as “VNF 10” (L, S025).

The orchestrator 20 confirming that the generation of “VNF 10” and “VNF21” determined to be generation targets in A (S004) is completedspecifies “VIM-NW” which is the VIM 40 for managing a network betweenthe data centers by Table T6 of FIG. 5(d) and a notification of IPaddresses of NW information of “VNF 10” and “VNF 21” from Table T21 ofFIG. 10(a) is provided to request a connection between VNFs (signal(10), S026). In “VIM-NW,” a process according to the request isperformed and its response is transmitted to the orchestrator 20 (S027).

Also, a notification of VNF types, VNF identification numbers,performance, and NW information of “VNF 10” and “VNF 21” received in thesignal (9) is provided in the signal (10) from the orchestrator 20 tothe OSS 51 (S028).

In the OSS 51, a signal (11) is received and the request content of thesignal (1) and the result of the signal (11) are associated and retainedas Table T2 of FIG. 10(a) (M, S029). “VNF 21” is added to Table T18 ofFIG. 9(c) provided in the VNFM 30 when “VNF 21” is generatedsubsequently to “VNF 10,” so that Table T23 of FIG. 10(c) is generated(N, 5030). Although Table T23 of FIG. 10(c) indicates information to bemanaged by the VNFM 30 (total), it may be managed for each VNFM 30 (foreach VNF 70 to be managed by the VNFM 30) (the same is true for TableT23 of FIG. 10(c) below).

After the completion of communication service generation, theorchestrator 20, the VNFM 30, and the VIM 40 retain information of TableT21 of FIG. 10(a), Table T23 of FIG. 10(c), and Table T16 of FIG. 9(a),respectively, and use the retained information in control such asenhancement, reduction, and termination of the service or a maintenanceoperation for malfunction, congestion, construction, etc.

For example, the VIM 40 specifies VM related to the hardware when ahardware malfunction occurs using information of Table T16 of FIG. 9(a)and the VNFM 30, which is its management function section, or theorchestrator 20 is notified of the specified VM and auto-healing ormaintenance personnel can cope with a malfunction. Also, even for anincrease/decrease or termination operation on VM, resources having aninfluence are specified and used to manage resource information.Likewise, the orchestrator 20 and the VNFM 30 also use thecorrespondence relationship between Table T21 of FIG. 10(a) and TableT23 of FIG. 10(c) to execute an operation such as enhancement,reduction, or termination on a communication service or an internalfunction.

Also, correspondence relationship information can also be aggregatedinto an operating system (OSS 51) of the entire communication networkand used to monitor/operate the entire communication network. The aboveprocess is a process when (1) instantiation is performed.

Next, a process when (2) auto-healing is performed will be describedusing sequence diagrams of FIGS. 17 and 18. Also, the sequence diagramillustrated in FIG. 18 is a continuation of the sequence diagram of FIG.17 (in a time-series manner). In the auto-healing, the VNF 70 to operatenormally is automatically generated when the VNF 70 does not operatenormally due to abnormality of hardware or software. Through theauto-healing, a communication function is automatically recovered in themobile communication system 1.

The OSS 51 operates while monitoring a state of the VNF 70 generated inan instantiation process (procedure) through the EMS 80 which is anoperation management system as in the conventional system. The EMS 80detecting abnormality (for example, non-response) of the VNF 70 duringthe operation notifies the OSS 51 of the abnormality (S101) and the OSS51 can re-arrange the VNF 70. An example in which the OSS 51 receivinginformation from the EMS 80 detecting an abnormal operation (forexample, non-response) of “VNF 10” between “VNF 10” and “VNF 21”generated in the instantiation process determines a rearrangement inwhich “VNF 10” is replaced and requests the orchestrator 20 to generatea replacement VNF 70 will be described.

A signal (1) in which a service ID used when a rearrangement source VNF70 is generated, a VNF identification number “VNF_001” for identifying arearrangement target, “100” which is a performance condition indicatingperformance to be rearranged (for example, a performance index valueequivalent to that of a current state), and a “separate DC” indicatingthe installation for a DC separate from the current DC as the NWcondition are set is transmitted from the OSS 51 to the orchestrator 20(S102).

In the orchestrator 20, the request reception section 21 receives aservice rearrangement request (S102, request reception step). In theorchestrator 20 receiving the service rearrangement request, the serviceID and the VNF identification number are used and the VNF type and thedata center are specified as information related to the VNF 70 of arearrangement source from data stored when the VNF 70 is generated. Thefact that the VNF type corresponding to the service ID and the VNFidentification number “VNF_001” is “VNF 10,” and the data center is “DC2” is derived from Table T21 of FIG. 10(a) and the fact that the VNFM 30of “VNF 10” is “VNFM 1” is derived from Table T3 of FIG. 5(b) (A, S103).

Next, the orchestrator 20 selects a data center in which “VNF 10” can bearranged using the operation condition of Table T4 of FIG. 5(c), the NWcondition input according to the signal (1), and the connectionconfiguration of the data center of Table T5 of FIG. 5(e) to rearrangethe above-described specified “VNF 10.” Candidates “DC 2,” “DC 3,” “DC4,” and “DC 5” can be obtained as the data center in which “VNF 10” canbe arranged from Table T4 of FIG. 5(c). Next, the candidate data centersare “DC 3” and “DC 5” based on connection information capable of beingobtained from Table T5 of FIG. 5(e) in which data centers connected to“DC 2” in which the VNF 70 of the rearrangement source is arranged are“DC 1,” “DC 3,” and “DC 5” as data centers separate from “DC 2” of therearrangement source VNF 70 from the input NW condition.

Next, the orchestrator 20 reads resource information of “DC 3” and “DC5” serving as the candidates from Table T1 of FIG. 4(a) of the networktotal resource information database accumulated through periodiccollection. The read resource information is shown in Table T31 of FIG.11(a). Next, a \INF identification number “VNF 010” is dispatched as anumber for uniquely identifying the VNF 70 to be rearranged (B,information).

Next, a combination table (Table T31 of FIG. 11(a)) of resourceinformation read to be “DC 3” and “DC 5” extracted as candidates for thedata center capable of being arranged in B (S104), a rearrangementsource VNF identification number “VNF_001,” a VNF type “VNF 10,” and aservice ID and “100” of the performance condition input in the signal(1) are transmitted as a necessary resource inquiry (signal (2)) to“VNFM 1” which is the VNFM 30 of “VNF 10” read in the above-described A(S103) (S105).

Also, an embodiment which does not include resource information of eachdata center in S105 is also possible. In this case, in place of theresource information of each data center, an identification number ofthe VIM 40 which manages each data center is read from Table T6 of FIG.5(d) and included in information to be transmitted in S106. For example,a combination in which the VIM 40 of “DC 3” is “VIM 1” and the VIM 40 of“DC 5” is “VIM 3” is included in information to be transmitted.

The signal (2) is received in “VNFM 1.” In “VNFM 1” receiving the signal(2), it is confirmed whether the resource information for each datacenter is set (whether the resource information is included in thesignal (2)). When the VIM identification number is set in place of theresource information, “VNFM 1” requests the VIM 40 to provide theresource information of each data center and collects the resourceinformation of each data center. For example, “VNFM 1” inquires of theresource information of “DC 3” for “VIM 1” and the resource informationof “DC 5” for the “VIM 3” received in the signal (2) and can obtainTable T31 of FIGS. 11(a) (S106 and S107).

In “VNFM 1” obtaining the resource information (Table T31 of FIG. 11(a))of the data center in the signal (2) or the processes of SI 06 and S107,detailed information of “VNF 10” set in the VNF type of the signal (2)is read from the VNF detailed information database previously retained(registered) in the retention section 31 of the “VNFM 1.” In thedetailed information, resource information (VM), resource information(NW), and function information according to a VNF internal structure anda performance condition of Table T9 of FIG. 6 are registered.

In “VNFM 1,” the resource information and the function informationnecessary for the performance condition “100” of the VNF type “VNF 10”received in the signal (2) from the read detailed information (Table T9of FIG. 6) are extracted (C1, S108).

An available data center is extracted by comparing the extractedresource information and function information with the availableresource information and the provided function of the resourceinformation (Table T31 of FIG. 11(a)) obtained in the signal (2) or theprocesses of S106 and S107. Specifically, it is determined that “VNF 10”requires “function 1” and “function 2” from Table T9 of FIG. 6 and “DC3” and “DC 5” of the candidates can provide “function 1” and “function2” together from Table T31 of FIG. 11(a).

Next, necessary resource information is derived to generate the VNF 70in resources provided by an available data center. Specifically, fromTable T31 of FIG. 11(a), it can be determined that “DC 3” can providelow CPU performance and “DC 5” can provide high CPU performance. This iscollated with the CPU performance of Table T9 of FIG. 6 read in theprocess of S108 and Table T32 of FIG. 11(b) can be obtained as acombination of resource information capable of being obtained by “DC 3”and “DC 5.” In detail, it can be seen that “VNF 10” is constituted ofthe internal functional sections “VNFC 100” and “VNFC 101” from Table T9of FIG. 6 read in the process of S108. Further, in the case of theperformance condition “100,” it can be seen that the internal functionalsection “VNFC 100” can be generated by virtual resources (VM and NW) ofthe model number “001” using the CPU performance “High” or the modelnumber “002” using the CPU performance “Low” and the internal functionalsection “VNFC 101” can be generated by virtual resources (VM and NW) ofthe model number “005” using the CPU performance “High” or the modelnumber “006” using the CPU performance “Low.” Therefore, the number ofcombinations of necessary virtual resources for generating the VNF 70having the performance condition “100” of the VNF type “VNF 10”indicated by the signal (2) is 1 in “DC 3” in which the CPU performance“Low” can be provided and is also 1 in “DC 5” in which the CPUperformance “High” can be provided, and Table T32 of FIG. 11(b) can beobtained as a combination of resource information capable of beingobtained by “DC 3” and “DC 5.” The service ID, the rearrangement VNFtype, and the rearrangement VNF identification number of the signal (2)and Table T9 of FIG. 6 of the detailed information are stored (C2,S109).

Next, Table T32 of FIG. 11(b) indicating the derived combination of theresource information and the data center is returned from “VNFM 1” tothe orchestrator 20 (signal (3), S110).

The orchestrator 20 receives the signal (3) through the reservationrequest section 22. A priority index of Table T12 of FIG. 5(f) isapplied to a combination table (Table T32 of FIG. 11(b)) of resourceinformation received in the signal (3) and data centers. It can bedetermined that the first priority is a bandwidth between data centersfrom Table T12 and a bandwidth between “DC 2” and “DC 3” is greater thanthe bandwidth between “DC 2” and “DC 3” and a bandwidth between “DC 2”and “DC 5” of the rearrangement source VNF 70 from Table T5 of FIG.5(e). On the basis of this, the priority is assigned and Table T33 ofFIG. 11(c) can be obtained (D, S111).

Next, reservation of the VIM 40 for managing the data center isperformed in the order of combination of high priority. The reservationrequest section 22 sets the necessary resources of combination 1 of “DC3” having highest priority and “DC 3” of the target in Table T33 of FIG.11(c) and a resource reservation request is transmitted to “VIM 1” whichis a management function of “DC 3” read from Table T6 of FIG. 5(d)(signal (4), S112, reservation request step). In the case of acombination of priority 1 of Table T33 of FIG. 11(c), information ofTable T34 of FIG. 12(a) becomes necessary resource information (VM andNW). When the resource reservation fails, a reservation request of thecombination of the next highest priority is generated (F, return fromthe process S115).

In “VIM 1,” a signal (4) is received. In “VIM 1” receiving the signal(4), the reservation section 42 confirms whether necessary resourcesshown in Table T34 of FIG. 12(a) for which “DC 3” set in the signal (4)is requested in the signal (4) can be secured on the basis of an insidemanagement area resource information database and a reservation number10 for which the resources are reserved is dispatched (E, S113,reservation step). In “VIM 1,” the reserved “DC 3” and reserved resourceinformation (Table T14) are stored along with the reservation number 10.In “VIM 1,” a reservation number serving as a response when theresources can be secured and an error serving as a response when theresources cannot be secured are provided to the orchestrator 20 (signal(5), S114).

In the orchestrator 20, a signal (5) from “VIM 1” is received. In theorchestrator 20 in which the signal (5) from “VIM 1” is received, aresource reservation result is confirmed (F, S115). When the reservationof the resources is impossible (F, NG of S115), reservation of acombination of the next highest priority is performed by returning tothe process of D (S111) again.

When the reservation succeeds, the orchestrator 20 sets the service IDwhen the rearrangement source VNF 70 is generated, “VIM 1” serving as aVIM identification number of a resource reservation destination, a VIMtype obtained from Table T6 of FIG. 5(d), a reservation number receivedin the signal (5) from “VIM 1,” and resource information of Table T34 ofFIG. 12(a) serving as reservation resource information (VM and NW) andrequests “VNFM 1” to rearrange “VNF 10” (signal (6), S116). Also, in theorchestrator 20, the service ID, the VNF type, the VNF identificationnumber, the reservation number, the reserved “VIM 1,” and the reserved“DC 3” are stored as information of the rearrangement VNF.

In “VNFM 1,” the virtual server generation request section 32 receivesthe signal (6). Next, the virtual server generation request section 32reads Table T9 of FIG. 6 of the detailed information stored in C2 (S109)from the service ID received in the signal (6) and determines thearrangement/startup information and the NW (network) configurationinformation corresponding to the model numbers “002” and “006” of TableT34 of FIG. 12(a) of the reserved resource information (VM and NW)received in the signal (6). Next, the virtual server generation requestsection 32 dispatches and assigns a VM identification number to thegenerated virtual machine (VM).

Next, in “VNFM 1,” a format of the arrangement/startup information andthe NW configuration information is changed according to the VIM typereceived in the signal (6) (detailed information is rewritten accordingto a management scheme of the VIM 40) by the virtual server generationrequest section 32 (G, S117, virtual server generation request step).

Next, the virtual server generation request section 32 notifies “VIM 1”of a reservation destination received in the signal (6) of thearrangement/startup information and the NW configuration information forwhich the format is changed for “VIM 1” and the reservation numberreceived in the signal (6) and requests “VIM 1” to generate “VNF 10”(signal (7), S118, virtual server generation request step). Informationset as the arrangement/startup information and the NW configurationinformation becomes Table T35 of FIG. 12(b). In “VNFM 1,” the serviceID, the VNF type, and the VNF identification number stored in C2 (S109)are stored in association with the VIM identification number and thereservation number received in the signal (6), the internal functionalsection read from Table T9 of FIG. 6, and the dispatched VMidentification number.

In “VIM 1,” the virtual server generation section 43 receives the signal(7). Next, the virtual server generation section 43 specifies resourcesof “DC 3” secured in the process of E (S113) as resources for startingup the VNF 70 from a reservation number received in the signal (7).Next, the virtual server generation section 43 reads image files of VMand the VNF in “DC 3” on the basis of the arrangement/startupinformation and the NW configuration information received in the signal(7) and generates/starts up VM and the VNF 70.

In “VIM 1,” the virtual server generation section 43 assigns “externalIP address 10” and “external IP address 11” as a number of externaladdresses designated in the signal (7) to VM from a pre-allocatedexternal IP address band. In “VIM 1,” information of Table T41 of FIG.14(a) is stored by associating the VM identification number of “VNFM 1”and the physical apparatus (HW) in addition to the reservation number ofthe process of E (S113) and the data center (H, S119 of FIG. 18, virtualserver generation step).

Next, the virtual server generation section 43 provides “VNFM 1” withTable T36 of FIG. 12(c) in which the external IP address allocatedduring VM generation is set as NW information as a response in a signal(8) (S120).

In “VNFM 1,” the NW information set in the signal (8) is added toinformation associated with a service ID stored in the process of G(S117) and stored. Content of the information becomes Table T37 of FIG.13(a) (J, S121). Although Table T37 of FIG. 13(a) shows information tobe managed by the VNFM 30 (total), it may be managed for each VNFM 30(for each VNF 70 to be managed by the VNFM 30) (the same is true forTable T37 of FIG. 13(a) below).

When VNF generation succeeds, a notification of the signal (9) in which“external IP address 10” and “external IP address 11” are set as NWinformation is provided from “VNFM 1” to the orchestrator 20 (S122).

In the orchestrator 20, the signal (9) is received. In the orchestrator20 receiving the signal (9), it is confirmed that the generation of theVNF 70 is completed. In the orchestrator 20, the information of therearranged VNF 70 stored in the process of S116 and the NW informationset in the signal (9) are added to Table T21 of FIG. 10(a) createdduring the generation in association with the service ID and stored.Content of the information becomes Table T38 of FIG. 13(b) (K, S123).

NW information of “VNF 21” which is the VNF 70 to which therearrangement source VNF 70 is connected is read from Table T38 of FIG.13(b) created during the generation and the NW connection is performed.A connection request in which “external IP address 20” for communicationof “VNF 21” read from Table T38 and “external IP address 10” forcommunication of the rearranged “VNF 10” received in the signal (9) areset is sent to “VIM-NW” to manage a network between VNFs 70 specifiedfrom Table T6 of FIG. 5(d) (signal (10), S124). In “VIM-NW,” the signal(10) is received and a response to the signal (10) is transmitted to theorchestrator 20 (S125). In “VIM-NW” in which the signal (10) isreceived, connections of “external IP address 20” and “external IPaddress 10” are performed (L, S126).

In the orchestrator 20, a response (S125) from “VIM-NW” for theconnection request of S124 is received. Next, when the connectionbetween the VNFs 70 is completed, the orchestrator 20 notifies the OSS51 of the VNF type, the VNF identification number, the performance, andthe NW information of “VNF 10” received in the signal (9) using a signal(11) (S127). The OSS 51 receives the signal (11) and retains Table T39of FIG. 13(c) in which request content of the signal (1) and a result ofthe signal (11) are associated and appended to Table T22 of FIG. 10(a)of the generation time (M, S128). Thereafter, the OSS 51 resumes theoperation by notifying “VNF 21” of NW information of the rearranged “VNF10” through the EMS 80 for a notification of switching of the opposite“VNF 10.” After confirming that communication of the rearranged “VNF 10”and “VNF 21” of a connection destination starts, the OSS 51 starts amaintenance operation such as stop or termination. The above process isa process when (2) auto-healing is performed.

Next, a process when (3) scale-out is performed using the sequencediagrams of FIGS. 19 and 20 will be described. Also, the sequencediagram illustrated in FIG. 20 is a continuation of the sequence diagramillustrated in FIG. 19 (in a time-series manner). In the scale-out, aVNF 70 having the same function as a relevant VNF 70 is generated inorder to distribute a load of the VNF 70 when the load of the VNF 70increases. According to the scale-out, an appropriate load distributionor the like is performed in the mobile communication system 1.

The OSS 51 operates while monitoring a state of the VNF 70 generated inan instantiation process (procedure) through the EMS 80 which is anoperation management system as in the conventional system. The EMS 80receives a notification of state information from the VNF 70 (S201) andtransmits the received state information to the OSS 51 (S202). Theabove-described process is performed periodically. On the basis of thestate information during the operation, the OSS 51 can detect a loadincrease of the VNF 70 and enhance the performance of the VNF 70 havingan increased load greater than a given level during the operation. Anexample in which the OSS 51 detecting the load increase of “VNF 10”between “VNF 10” and “VNF 21” generated in the instantiation processdetermines the enhancement of 100% of the performance of the VNF 70 andsends a request to the orchestrator 20 will be described.

A signal (1) in which a service ID used when an enhancement source VNF70 is generated, a VNF identification number “VNF_001” for identifyingan enhancement target, “100” which is a performance condition indicatingperformance to be enhanced (for example, a performance index valueequivalent to that of a current state), and a “separate DC” indicatingthe installation for a DC separate from the current DC as the NWcondition are set is transmitted from the OSS 51 to the orchestrator 20(S203).

In the orchestrator 20, the request reception section 21 receives aservice enhancement request (S203, request reception step). In theorchestrator 20 receiving the service enhancement request, the serviceID and the VNF identification number are used and the VNF type and thedata center are specified as information related to the VNF 70 of anenhancement source from data stored when the VNF 70 is generated. Thefact that the VNF type corresponding to the service ID and the VNFidentification number “VNF_001” is “VNF 10,” and the data center is “DC2” is derived from Table T21 of FIG. 10(a) and the fact that the VNFM 30of “VNF 10” is “VNFM 1” is derived from Table T3 of FIG. 5(b) (A, S204).

Next, the orchestrator 20 selects a data center in which “VNF 10” can bearranged using the operation condition, the NW condition input accordingto the signal (1), and the connection configuration of the data centerof Table T5 of FIG. 5(e) to enhance the above-described specified “VNF10.” Candidates “DC 2,” “DC 3,” “DC 4,” and “DC 5” can be obtained asthe data center in which “VNF 10” can be arranged from Table T4 of FIG.5(c). Next, the candidate data centers become “DC 3” and “DC 5” based onconnection information capable of being obtained from Table T5 of FIG.5(e) in which data centers connected to “DC 2” in which VNFs 70 of anenhancement source and a connection destination are arranged are “DC 1,”“DC 3,” and “DC 5” as data centers separate from “DC 2” of theenhancement source VNF 70 from the input NW condition.

Next, the orchestrator 20 reads resource information of “DC 3” and “DC5” serving as the candidates from Table T1 of FIG. 4(a) of the networktotal resource information database accumulated through periodiccollection. The read resource information is shown in Table T31 of FIG.11(a). Next, a VNF identification number “VNF_010” is dispatched as anumber for uniquely identifying the VNF 70 to be enhanced (B, S205).

Next, an enhancement VNF identification number “VNF_010,” Table T31 ofFIG. 11(a) serving as information of candidates for the data centercapable of being arranged, a VNF type “VNF 10,” “VNF_001” in theenhancement source VNF identification number, and a service ID and “100”of the performance condition input in the signal (1) are transmitted asa necessary resource inquiry (signal (2)) to “VNFM 1” which is the VNFM30 of “VNF 10” read in the above-described A (S204) (S206).

Also, an embodiment which does not include resource information of eachdata center in S206 is also possible. In this case, in place of theresource information of each data center, an identification number ofthe VIM 40 which manages each data center is read from Table T6 of FIG.5(d) and included in information to be transmitted in S206. For example,a combination in which the VIM 40 of “DC 3” is “VIM 1” and the VIM 40 of“DC 5” is “VIM 3” is included in information to be transmitted.

The signal (2) is received in “VNFM 1.” In “VNFM 1” receiving the signal(2), it is confirmed whether the resource information for each datacenter is set (whether the resource information is included in thesignal (2)). When the VIM identification number is set in place of theresource information, “VNFM 1” requests the VIM 40 to provide theresource information of each data center and collects the resourceinformation of each data center. For example, “VNFM 1” inquires of theresource information of “DC 3” for “VIM 1” and the resource informationof “DC 5” for the “VIM 3” received in the signal (2) and can obtainTable T31 of FIGS. 11(a) (S207 and S208).

In “VNFM 1” obtaining the resource information (Table T31 of FIG. 11(a))of the data center in the signal (2) or the processes of S207 and S208,detailed information of “VNF 10” set in the VNF type of the signal (2)is read from the VNF detailed information database previously retained(registered) in the retention section 31 of the “VNFM 1.” In thedetailed information, resource information (VM), resource information(NW), and function information according to a VNF internal structure anda performance condition of Table 19 of FIG. 6 are registered.

In “VNFM 1,” the resource information and the function informationnecessary for the performance condition “100” of the VNF type “VNF 10”received in the signal (2) from the read detailed information (Table T9of FIG. 6) are extracted (C1, S209).

An available data center is extracted by comparing the extractedresource information and function information with the availableresource information and the provided function of the resourceinformation (Table T31 of FIG. 11(a)) capable of being obtained in thesignal (2) or the processes of S207 and S208. Specifically, it isdetermined that “VNF 10” requires “function 1” and “function 2” fromTable T9 of FIG. 6 and “DC 3” and “DC 5” of the candidates can provide“function 1” and “function 2” together from Table T31 of FIG. 11(a).

Next, necessary resource information is derived to generate the VNF 70in resources provided by an available data center. Specifically, fromTable T31 of FIG. 11(a), it can be determined that “DC 3” can providelow CPU performance and “DC 5” can provide high CPU performance. This iscollated with the CPU performance of Table T9 of FIG. 6 read in theprocess of S209 and Table T32 of FIG. 11(b) can be obtained as acombination of resource information capable of being obtained by “DC 3”and “DC 5.” In detail, it can be seen that “VNF 10” is constituted ofthe internal functional sections “VNFC 100” and “VNFC 101” from Table T9of FIG. 6 read in the process of S209. Further, in the case of theperformance condition “100,” it can be seen that the internal functionalsection “VNFC 100” can be generated by virtual resources (VM and NW) ofthe model number “001” using the CPU performance “High” or the modelnumber “002” using the CPU performance “Low” and the internal functionalsection “VNFC 101” can be generated by virtual resources (VM and NW) ofthe model number “005” using the CPU performance “High” or the modelnumber “006” using the CPU performance “Low.” Therefore, the number ofcombinations of necessary virtual resources for generating the VNF 70having the performance condition “100” of the VNF type “VNF 10”indicated by the signal (2) is 1 in “DC 3” in which the CPU performance“Low” can be provided and is also 1 in “DC 5” in which the CPUperformance “High” can be provided, and Table T32 of FIG. 11(b) can beobtained as a combination of resource information capable of beingobtained by “DC 3” and “DC 5.” The service ID, the enhancement VNF type,and the enhancement VNF identification number of the signal (2) andTable T9 of FIG. 6 of the detailed information are stored (C2, S210).

Next, Table T32 of FIG. 11(b) indicating the derived combination of theresource information and the data center is returned from “VNFM 1” tothe orchestrator 20 (signal (3), S211),

The orchestrator 20 receives the signal (3) through the reservationrequest section 22. A priority index of Table T12 of FIG. 5(f) isapplied to a combination table (Table T32 of FIG. 11(b)) of resourceinformation received in the signal (3) and data centers. It can bedetermined that the first priority is a bandwidth between data centersfrom Table T12 and a bandwidth between “DC 2” and “DC 3” is greaterbetween the bandwidth between “DC 2” and “DC 3” and a bandwidth between“DC 2” and “DC 5” of “VNF 21” of the connection destination VNF 70 fromTable T5 of FIG. 5(e). On the basis of this, the priority is assignedand Table T33 of FIG. 11(c) can be obtained (D, S212).

Next, reservation for the VIM 40 for managing the data center isperformed in the order of combination of high priority. The reservationrequest section 22 sets the necessary resources of combination 1 of “DC3” having highest priority and “DC 3” of the target in Table T33 of FIG.11(c) and a resource reservation request is transmitted to “VIM 1” whichis a management function of “DC 3” read from Table T6 of FIG. 5(d)(signal (4), S213, reservation request step). In the case of acombination of priority 1 of Table T33 of FIG. 11(c), information ofTable T34 of FIG. 12(a) becomes necessary resource information (VM andNW). When the resource reservation fails, a reservation request of thecombination of the next highest priority is generated (F, return fromthe process S216).

In “VIM 1,” the signal (4) is received. In “VIM 1” receiving the signal(4), the reservation section 42 confirms whether necessary resourcesshown in Table T34 of FIG. 12(a) for which “DC 3” set in the signal (4)is requested in the signal (4) can be secured on the basis of an insidemanagement area resource information database and a reservation number10 for which the resources are reserved is dispatched (E, S214,reservation step). In “VIM 1,” the reserved “DC 3” and reserved resourceinformation are stored along with the reservation number 10. In “VIM 1,”a reservation number serving as a response when the resources can besecured and an error serving as a response when the resources cannot besecured are provided to the orchestrator 20 (signal (5), S215).

In the orchestrator 20, a signal (5) from “VIM 1” is received. In theorchestrator 20 in which the signal (5) from “VIM 1” is received, aresource reservation result is confirmed (F, S216). When the reservationof the resources is impossible (F, NG of S216), reservation of acombination of the next highest priority is performed by returning tothe process of D (S212) again.

When the reservation succeeds, the orchestrator 20 sets the service IDwhen the enhancement source VNF 70 is generated, “VIM 1” serving as aVIM identification number of a resource reservation destination, a VIMtype obtained from Table T6 of FIG. 5(d), a reservation number receivedin the signal (5) from “VIM 1,” and resource information of Table T34 ofFIG. 12(a) serving as reservation resource information (VM and NW) andrequests “VNFM 1” to enhance “VNF 10” (signal (6), S217). Also, in theorchestrator 20, the service ID, the VNF type, the VNF identificationnumber, the reservation number, the reserved “VIM 1,” and the reserved“DC 3” are stored as information of the enhancement VNF.

In “VNFM 1,” the virtual server generation request section 32 receivesthe signal (6). Next, the virtual server generation request section 32reads Table T9 of FIG. 6 of the detailed information stored in C2 (S210)from the service ID received in the signal (6) and determines thearrangement/startup information and the NW (network) configurationinformation corresponding to the model numbers “002” and “006” of TableT34 of FIG. 12(a) of the reserved resource information (VM and NW)received in the signal (6). Next, the virtual server generation requestsection 32 dispatches and assigns a VM identification number to thegenerated virtual machine (VM).

Next, in “VNFM 1,” a format of the arrangement/startup information andthe NW configuration information is changed according to the VIM typereceived in the signal (6) (detailed information is rewritten accordingto a management scheme of the VIM 40) by the virtual server generationrequest section 32 (G S218, virtual server generation request step).

Next, the virtual server generation request section 32 notifies “VIM 1”of a reservation destination received in the signal (6) of thearrangement/startup information and the NW configuration information forwhich, the format is changed for “VIM 1” and the reservation numberreceived in the signal (6) and requests “VIM 1” to generate “VNF 10”(signal (7), S219, virtual server generation request step). Informationset as the arrangement/startup information and the NW configurationinformation becomes Table T35 of FIG. 12(b). In “VNFM 1,” the serviceID, the VNF type, and the VNF identification number stored in C2 (S210)are stored in association with the VIM identification number and thereservation number received in the signal (6), the internal functionalsection read from Table T9 of FIG. 6, and the dispatched VMidentification number.

In “VIM 1,” the virtual server generation section 43 receives the signal(7). Next, the virtual server generation section 43 specifies resourcesof “DC 3” secured in the process of E (S214) as resources for startingup the VNF 70 from a reservation number received in the signal (7).Next, the virtual server generation section 43 reads image files of VMand the \INF in “DC 3” on the basis of the arrangement/startupinformation and the NW configuration information received in the signal(7) and generates/starts up VM and the VNF 70.

In “VIM 1,” the virtual server generation section 43 assigns “externalIP address 10” and “external IP address 11” as a number of externaladdresses designated in the signal (7) to VM from a pre-allocatedexternal IP address band. In “VIM 1,” information of Table T41 of FIG.14(a) is stored by associating the VM identification number of “VNFM 1,”the allocated resource information, and the physical apparatus (HW) inaddition to the reservation number of the process of E (S214) and thedata center (H, S220 of FIG. 20, virtual server generation step).

Next, the virtual server generation section 43 provides “VNFM 1” withTable T36 of FIG. 12(c) in which the external IP address allocatedduring VM generation is set as NW information as a response in a signal(8) (S221).

In “VNFM 1,” the NW information set in the signal (8) is added toinformation associated with a service ID stored in the process of G(S218) and stored. Content of the information becomes Table T37 of FIG.13(a) (J, S222).

When VNF generation succeeds, a notification of a signal (9) in which“external IP address 10” and “external IP address 11” are set as NWinformation is provided from “VNFM 1” to the orchestrator 20 (S223).

In the orchestrator 20, the signal (9) is received. In the orchestrator20 receiving the signal (9), it is confirmed that the generation of theVNF 70 is completed. In the orchestrator 20, the information of theenhanced VNF 70 stored in the process of S217 and the NW information setin the signal (9) are added to Table T21 of FIG. 10(a) created duringthe generation in association with the service ID and stored. Content ofthe information becomes Table T38 of FIG. 13(b) (K, S224).

NW information of “VNF 21” which is the VNF 70 to which the enhancementsource VNF 70 is connected is read from Table T38 of FIG. 13(b) createdduring the generation and the NW connection is performed. A connectionrequest in which “external IP address 20” for communication of “VNF 21”read from Table T38 and “external IP address 10” for communication ofthe enhanced “VNF 10” received in the signal (9) are set is sent to“VIM-NW” to manage a network between VNFs 70 specified from Table T6 ofFIG. 5(d) (signal (10), S225). In “VIM-NW,” the signal (10) is receivedand a response to the signal (10) is transmitted to the orchestrator 20(S226). In “VIM-NW” in which the signal (10) is received, connections of“external IP address 20” and “external IP address 10” are performed (L,S227).

In the orchestrator 20, a response (S226) from “VIM-NW” for theconnection request of S225 is received. Next, when the connectionbetween the VNFs 70 is completed, the orchestrator 20 notifies the OSS51 of the VNF type of “VNF 10,” the VNF identification number, theperformance, and the NW information received in the signal (9) using asignal (11) (S228). The OSS 51 receives the signal (11) and retainsTable T39 of FIG. 13(c) in which request content of the signal (1) and aresult of the signal (11) are associated and appended to Table T22 ofFIG. 10(a) of the generation time (M, S229). The above process is aprocess when (3) scale-out is performed.

Next, a process when (4) scale-in is performed using the sequencediagrams of FIGS. 21 and 22 will be described. Also, the sequencediagram illustrated in FIG. 22 is a continuation of the sequence diagramillustrated in FIG. 21 (in a time-series manner). In the scale-in, VNFs70 may be aggregated when there are a plurality of VNFs 70 having thesame function with a low load or the like. According to the scale-in,the appropriate use of resources is performed in the mobilecommunication system 1.

The OSS 51 operates while monitoring a state of the VNF 70 that isgenerated in an instantiation process (procedure) through the EMS 80which is an operation management system as in the conventional systemand is further enhanced in the scale-out process (procedure). The EMS 80receives a notification (signal (1)) of state information from the VNF70 (S301) and transmits the received state information (signal (1)) tothe OSS 51 (S302). The above-described process is performedperiodically. On the basis of the state information during theoperation, the OSS 51 can detect a load decrease of VNF and reduce theperformance of the VNF 70 having a decreased load less than a givenlevel during the operation. An example in which the OSS 51 detecting thedecreased load less than the given level for a plurality of “VNFs 10”enhanced in the above-described scale-out process determines thereduction of the total performance of the VNF 10 and sends a request tothe orchestrator 20 will be described.

In the OSS 51, management is performed as shown in Table T39 of FIG.13(c) for a service type of the VNF 70 generated, enhanced, or reducedthrough the orchestrator 20.

Even when a load amount of the VNF 70 is periodically collected from theVNF 70 as in the above-described signal (1) and VNFs 70 having the samefunction are integrated in the OSS 51, scale-in integration ofdistributed processing is determined as long as a load sufficientlyfalls within a rated load. For example, in the OSS 51, a VNF having asmaller load amount among a plurality of VNFs 70 (“VNF_001” and“VNF_010”) acquired in the signal (1) (message (1)) becomes a deletiontarget (A, S303).

In the OSS 51, Table T39 of FIG. 13(c) is referred to, an opposite node(“VNF_021” in Table T39) connected to the VNF 70 serving as the deletiontarget is determined in the same service, and a configuration change isindicated by a signal (2) via the EMS 80 so that newly generated trafficfor the opposite node is not transmitted to the VNF 70 (“VNF_010”) ofthe deletion target (S304 and S305).

The signal (2) is received in “VNF_021,” the configuration change isperformed so that no new traffic is transmitted to the VNF 70(“VNF_010”) of the deletion target for traffic for which the load isdistributed to “VNF_001” and “VNF_010” opposite to each other (S306),and a response message (3) (signal (3)) is returned to the OSS 51 viathe EMS 80 (S307 and S308).

In the OSS 51, the response message (3) (signal (3)) is received. Next,in the OSS 51, the VNF 70 (“VNF_010”) serving as the deletion target isobstructed by a message (4) (signal) via the EMS 80 and a user expulsionrequest is generated (5309 and S310).

In “VNF_010,” the completion of a process on already accommodated usertraffic is awaited (or the process is forcibly terminated) and theprocess converges (C, S311). Next, a response message (5) (signal (5))is returned from “VNF_010” to the OSS 51 via the EMS 80 (S312 and S313).

In the OSS 51, the response message (5) (signal (5)) is received. Next,in the OSS 51, a signal (6) in which the service ID used during VNFgeneration, a VNF identification number “VNF_010” for identifying areduction target, a performance condition indicating performance to bereduced, and “100” which is a performance value desired to be reducedare set is generated (S314) and transmitted as a service reductionrequest to the orchestrator 20 (S315 of FIG. 22).

In the orchestrator 20, a service reduction request is received. In theorchestrator 20 receiving the service reduction request, the service IDand the VNF identification number are used and the VNF type and the datacenter are specified as information related to the VNF 70 of thereduction target from data stored when the VNF 70 is created orenhanced. The fact that the VNF type corresponding to the service ID andthe VNF identification number “VNF_010” is “VNF 10,” and the data centeris “DC 3” is derived from Table T38 of FIG. 13(b) and the fact that theVNFM 30 of “VNF 10” is “VNFM 1” is derived from Table T3 of FIG. 5(b)(E, S316).

Next, the orchestrator 20 can obtain a service ID when the VNF 70serving as the deletion target is generated, the VNF type serving as thedeletion target, the VNF identification number, the VIM identificationnumber (“VIM 1”) of the reservation destination, and the reservationnumber (“10”) from Table T38 of FIG. 13(b) in order to delete theabove-described specified “VNF_010” (F, S317). The orchestrator 20requests “VNFM 1” to delete “VNF_010” by a signal (7) including theinformation (S318).

In “VNFM 1,” the signal (7) is received. In “VNFM 1,” the service ID,the VNF type, the VNF identification number, the VIM identificationnumber, and the reservation number can be obtained from the VNFreduction request message received in the signal (7) and a reductionprocedure can be obtained from Table T9 of FIG. 6(a) (G, S319). Next,“VNFM 1” requests “VIM 1” to reduce the relevant VM according to thereservation number by a signal (8) which is the VNF reduction requestmessage (S320).

In “VIM 1,” the reservation number can be obtained from the VNFreduction request message received in the signal (8) and the reductionof VM is executed by obtaining the DC number “DC 3” serving as thedeletion target and the VM identification number from Table T41 of FIG.14(a) (H, S321). Next, in “VIM 1,” a VNF reduction response is returnedto the orchestrator 20 via “VNFM 1” by a signal (9) (S322 and S323). In“VNFM 1,” Table T23 of FIG. 10(c) obtained by deleting “VNF_010” fromTable T37 of FIG. 13(a) is retained.

In the orchestrator 20, the VNF reduction response (VNF deletionresponse message) is received. Next, in the orchestrator 20, a releaserequest of a connection between VNFs 70 performing deletion is generatedfrom Table T38 of FIG. 13(b) (J, S324) and transmitted to “VIM-NW” by asignal (10) (S325).

In “VIM-NW,” the signal (10) is received and a response to the releaserequest is performed (S326). Also, in “VIM-NW,” the connection betweenVNFs 70 is released (K, S327).

In the orchestrator 20, the response from “VIM-NW” is received, TableT21 of FIG. 10(a) obtained by deleting “VNF 010” from Table T38 of FIG.13(c) is retained, and the service reduction response is sent to the OSS51 by a signal (11) (S328).

In the OSS 51, the request content of the signal (1) and the result ofthe signal (11) are associated and information of Table T43 of FIG.14(b) obtained by reducing VNF from Table T39 of FIG. 13(c) during thegeneration is retained (S329). The above process is a process when (4)scale-in is performed.

Although an enhancement/reduction procedure is shown in units of virtualcommunication functions (VNFs 70) in the above-described embodiment, theVNF 70 is generally constituted of one or more internal functionalsections (VNFCs) and an enhancement/reduction operation is also executedin units of internal functional sections.

In the above-described present embodiment, VNF detailed information(Table T9 of FIG. 6) in common with instantiation in scale-out,scale-in, and auto-healing is used. However, enhancement/reduction of aunit of an internal functional section is possible if a procedure ofextracting an enhancement/reduction pattern of the internal functionalsection which satisfies a performance condition designated on the basisof a combination of internal functional sections of the VNF 70previously registering and generating (starting up) theenhancement/reduction pattern of the unit of the internal functionalsection as VNF detailed information is added.

At this time, it is necessary to designate a VNF identification numberfor identifying an operation target of a unit of VNF as an identifiercapable of specifying an operation of the unit of the internalfunctional section. For example, the upper-limit number of internalfunctional sections (Table TX of FIG. 26(a)) within one VNF and anenhancement/deletion pattern of a unit of a VNF internal function (TableTY of FIG. 26(b)) are additionally pre-registered as detailedinformation in the database of the VNFM 30.

The scale-out process is performed as follows. When detailed informationof an enhancement source VNF is read in a process (procedure) C1 in thescale-out process of FIG. 19, a determination of the enhancement unitillustrated in the flowchart of FIG. 24 is added. An example in whichthe performance condition “100” is received as the enhancement of VNF 10in the signal (2) of S206 will be described. The detailed information(Table T37 of FIG. 13(a)) of the enhancement source VNF is read in theprocess (procedure) C1, the number of VMs of the enhancement source VNFis compared with the upper-limit number of Table TX of FIG. 26(a), andit is determined that the enhancement of the unit of VNFC is performedwhen the number of VMs is less than the upper-limit number. Next, aconfiguration of the model number “101” is extracted as resourceinformation and function information necessary for the performancecondition “100” from Table TY of FIG. 26(b) pre-registered in the VNFM30.

Whether the unit of enhancement is designated as the unit of the VNF 70or the unit of the internal functional section can be indicated from theOSS 51 without being determined by the VNFM 30. After the enhancementpattern of the unit of the internal functional section is extracted fromTable TY, a similar procedure to the embodiment of the above-describedscale-out is applied.

The scale-in process is performed as follows. When detailed informationof the reduced VNF is read in the process (procedure) G in the scale-inprocess of FIG. 22, the determination of a unit of reduction illustratedin the flowchart of FIG. 25 is added and one reduction pattern isextracted. For the VNFM 30 to determine the unit of reduction, the OSS51 sends a request to the VNFM 30 by including the performance condition“100” received in the signal (6) in the signal (7) in the sequencediagram of FIG. 22. The VNFM 30 can obtain the VNF identification numberand the performance condition from the received signal (7). The VNFM 30″reads detailed information (Table T37 of FIG. 13(a)) of a reductionsource VNF to be retained on the basis of the VNF identification numberreceived in the signal (7), compares the number of VMs of the reductionsource VNF with the minimum number of components of the table of FIG.26(a), and it is determined that the reduction of the unit of VNFC isperformed in the case of a minimum configuration. Next, a configurationof the model number “101” is extracted as resource information andfunction information corresponding to the performance condition “100”from Table TY of FIG. 26(b) pre-registered in the VNFM 30 and resourcesof the reduction target and the procedure are obtained.

Whether the unit of reduction is designated as the unit of the VNF 70 orthe unit of the internal functional section can be indicated from theOSS 51 without being determined by the VNFM 30. After the reductionpattern of the unit of the internal functional section is extracted fromTable TY, a similar procedure to the embodiment of the above-describedscale-in is applied.

The relationship between the unit of a performance increase/decrease ofa virtualization function and an embodiment is illustrated in FIG. 27.

A variation of the embodiment of the present invention is illustrated inFIG. 28. In FIG. 28, the term “selection” refers to the extraction of aresource area (VIM 40/data center) serving as a candidate. The term“reservation” refers to making a request for resource reservation from acandidate area. The term “arrangement plan” refers to arrangement plancreation of the VNF 70 for reserved resources. The term “allocation”refers to the allocation of resources (generation of the VNF 70) basedon the arrangement plan. The term “detailed condition” refers to thecondition for creating the arrangement plan. The term “condition” refersto the condition obtained by abstracting the detailed condition. Theterm “total” refers to total resource information. The term “inside anarea” refers to resource information inside a management area. Also, asshown in an area indicated by a broken line in FIG. 28, resourceinformation which is not proprietary can be obtained through any path.

The above-described embodiment has a pattern in which the VNFM 30selects the VIM 40 (data center), the VNFM 30 generates the arrangementplan of the VNF 70, and the VNFM 30 instructs that the VNF 70 for theVIM 40 be generated (a second pattern from the left among patterns ofFIG. 28). However, a pattern in which the selection of the VIM (datacenter) 40 is performed by the orchestrator 20 in place of the VNFM 30(a first pattern from the left among the patterns of FIG. 28) may beprovided.

In the management system 10 according to the present embodiment, the VIM40 is requested to generate the VNF 70 using detailed informationretained by the VNFM 30. Accordingly, the VNF 70 is generated withouthaving to provide a notification of detailed information (specifically,arrangement/startup information and NW configuration information ofTable T9 of FIG. 6) from the VNFM 30 to the orchestrator 20. That is,according to the management system 10 according to the presentembodiment, it is possible to prevent the leakage of detailedinformation for implementing the VNF 70 to execute a communicationprocess on virtualization resources. Thereby, multi-vendor applicationscan be promoted.

For example, even when the VNFM 30 and the orchestrator 20 are providedby separate vendors, detailed information of the VNF 70 which is theknow-how of the vendor for providing the VNFM 30 is not leaked to thevendor of the orchestrator 20.

Also, although a mobile communication system for providing a function ofmobile communication to a mobile communication terminal is provided inthe above-described embodiment, it is unnecessary for the presentinvention to be the mobile communication system. The present inventioncan be applied to a fixed communication system for providing a functionof fixed communication to a fixed communication terminal. The fixedcommunication terminal and the fixed communication system are differentfrom the above-described mobile communication system and connected bywire. The above-described embodiment may be an embodiment of a fixedcommunication system according to the present invention if the mobilecommunication terminal is replaced with the fixed communicationterminal, the mobile communication is replaced with the fixedcommunication, and the mobile communication system is replaced with thefixed communication system. However, in this case, a specific node is anode according to the fixed communication system. Also, the presentinvention can be executed in a communication system in which mobilecommunication and fixed communication are mixed.

That is, the present invention is not limited to the mobilecommunication terminal, the mobile communication, and the mobilecommunication system, but can be applied to any communication terminal,any communication, and any communication system as long as a similarframework to the above-described embodiment is provided.

REFERENCE SIGNS LIST

1 Mobile communication system

10 Management system

20 Orchestrator

21 Request reception section

22 Reservation request section

30 VNFM

31 Retention section

32 Virtual server generation request section

40 VIM

41 Monitoring section

42 Reservation section

43 Virtual server generation section

50 OSS/BSS

51 OSS

60 NFVI

70 VNF

80 EMS

101 CPU

102 RAM

103 ROM

104 Communication module

105 Auxiliary storage apparatus

1. A management system which is included in a communication systemconfigured to include virtualization resources including a physicalserver in which a virtual server for executing a communication processis generated and which includes a virtual communication-functionmanagement node for managing a function of executing the communicationprocess provided in the virtual server, a virtualization resourcemanagement node for managing the virtualization resources, and anoverall management node for managing all the virtualization resources,wherein the virtualization resource management node includes circuitryconfigured to: monitor a use state of the virtualization resources;perform reservation by receiving a request of the reservation ofnecessary resources for generation of the virtual server among thevirtualization resources; and generate the virtual server by receiving arequest for generating the virtual server on the necessary resources forthe generation of the virtual server reserved, wherein the overallmanagement node includes circuitry configured to: receive a requestrelated to a function of the communication process accompanied by thegeneration of the virtual server in the physical server, wherein themanagement system includes circuitry configured to: calculate thenecessary resources for the generation of the virtual server on thebasis of the request received and the use state of the virtualizationresources monitored and request the virtualization resource managementnode to perform the reservation, and wherein the virtualcommunication-function management node includes circuitry configured to:retain detailed information for implementing the virtual server on thevirtualization resources; and generate the request for generating thevirtual server on the necessary resources reserved using the detailedinformation retained for the virtualization resource management node. 2.The management system according to claim 1, comprising: a plurality ofvirtualization resource management nodes configured to manage thevirtualization resources in mutually different schemes, wherein thevirtual communication-function management node requests the generationof the virtual server by rewriting the detailed information according toa virtualization resource management schemes by the virtualizationresource management node.
 3. A virtual communication-function managementnode in a management system which is included in a communication systemconfigured to include virtualization resources including a physicalserver in which a virtual server for executing a communication processis generated and which includes the virtual communication-functionmanagement node for managing a function of executing the communicationprocess provided in the virtual server, a virtualization resourcemanagement node for managing the virtualization resources, and anoverall management node for managing all the virtualization resources,the virtual communication-function management node comprising circuitryconfigured to: retain detailed information for implementing the virtualserver on the virtualization resources; and a request the virtualizationresource management node to generate the virtual server on the reservedresources necessary for the generation of the virtual server among thevirtualization resources using the detailed information retained.
 4. Amanagement method which is a method of operating a management systemwhich is included in a communication system configured to includevirtualization resources including a physical server in which a virtualserver for executing a communication process is generated and whichincludes a virtual communication-function management node for managing afunction of executing the communication process provided in the virtualserver, a virtualization resource management node for managing thevirtualization resources, and an overall management node for managingall the virtualization resources, wherein the virtualcommunication-function management node includes circuitry configured to:a retain detailed information for implementing the virtual server on thevirtualization resources, and wherein the management method includes: amonitoring step of monitoring, by the virtualization resource managementnode, a use state of the virtualization resources; a reservation step ofperforming, by the virtualization resource management node, reservationby receiving a request of a reservation of resources necessary for thegeneration of the virtual server among the virtualization resources; avirtual server generation step of generating, by the virtualizationresource management node, the virtual server by receiving a request forgenerating the virtual server on the necessary resources for thegeneration of the virtual server reserved in the reservation step; arequest reception step of receiving, by the overall management node, arequest related to a function of the communication process accompaniedby the generation of the virtual server in the physical server; areservation request step of calculating, by the management system, thenecessary resources for the generation of the virtual server on thebasis of the request received in the request reception step and the usestate of the virtualization resources monitored in the monitoring stepand requesting the virtualization resource management node to performthe reservation; and a virtual server generation request step ofrequesting, by the virtual communication-function management node, thegeneration of the virtual server on the necessary resources reserved inthe reservation step using the detailed information retained for thevirtualization resource management node.
 5. A management method which isa method of operating a virtual communication-function management nodein a management system which is included in a communication systemconfigured to include virtualization resources including a physicalserver in which a virtual server for executing a communication processis generated and which includes the virtual communication-functionmanagement node for managing a function of executing the communicationprocess provided in the virtual server, a virtualization resourcemanagement node for managing the virtualization resources, and anoverall management node for managing all the virtualization resources,wherein the virtual communication-function management node includescircuitry configured to: retain detailed information for implementingthe virtual server on the virtualization resources, and wherein themanagement method includes: a virtual server generation request step ofrequesting the virtualization resource management node to generate thevirtual server on the reserved resources necessary for the generation ofthe virtual server among the virtualization resources using the detailedinformation retained.